SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
Apex

Apex static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your APEX code

  • All rules 56
  • Vulnerability1
  • Bug12
  • Security Hotspot3
  • Code Smell40
 
Tags
    Impact
      Clean code attribute
        1. Test methods should not be annotated with "@isTest(SeeAllData=true)"

           Code Smell
        2. Tested code should be enclosed between "Test.StartTest()" and "Test.StopTest()"

           Code Smell
        3. Messages should not be hardcoded

           Code Smell
        4. System.runAs should be used to test user permissions

           Code Smell
        5. Business logic should not be implemented inside Triggers

           Code Smell
        6. Multi-line comments should not be empty

           Code Smell
        7. Methods should not have identical implementations

           Code Smell
        8. Cognitive Complexity of functions should not be too high

           Code Smell
        9. Track parsing failures

           Code Smell
        10. Boolean checks should not be inverted

           Code Smell
        11. Two branches in a conditional structure should not have exactly the same implementation

           Code Smell
        12. "switch" statements should not be nested

           Code Smell
        13. Unused local variables should be removed

           Code Smell
        14. "switch" statements should not have too many "case" clauses

           Code Smell
        15. Track lack of copyright and license headers

           Code Smell
        16. Functions should not have too many lines of code

           Code Smell
        17. Control flow statements "if", "for", "while", "switch" and "try" should not be nested too deeply

           Code Smell
        18. "switch" statements should have "when else" clauses

           Code Smell
        19. "if ... else if" constructs should end with "else" clauses

           Code Smell
        20. Sections of code should not be commented out

           Code Smell
        21. Statements should be on separate lines

           Code Smell
        22. String literals should not be duplicated

           Code Smell
        23. Methods should not be empty

           Code Smell
        24. Unused function parameters should be removed

           Code Smell
        25. Local variable and method parameter names should comply with a naming convention

           Code Smell
        26. "when" clauses should not have too many lines of code

           Code Smell
        27. Unused "private" methods should be removed

           Code Smell
        28. Track uses of "TODO" tags

           Code Smell
        29. Track uses of "FIXME" tags

           Code Smell
        30. Boolean literals should not be redundant

           Code Smell
        31. Redundant pairs of parentheses should be removed

           Code Smell
        32. Nested blocks of code should not be left empty

           Code Smell
        33. Functions should not have too many parameters

           Code Smell
        34. Expressions should not be too complex

           Code Smell
        35. Mergeable "if" statements should be combined

           Code Smell
        36. Tabulation characters should not be used

           Code Smell
        37. Files should not have too many lines of code

           Code Smell
        38. Lines should not be too long

           Code Smell
        39. Class names should comply with a naming convention

           Code Smell
        40. Function names should comply with a naming convention

           Code Smell

        Unused local variables should be removed

        intentionality - clear
        maintainability
        Code Smell
        • unused

        Why is this an issue?

        How can I fix it?

        An unused local variable is a variable that has been declared but is not used anywhere in the block of code where it is defined. It is dead code, contributing to unnecessary complexity and leading to confusion when reading the code. Therefore, it should be removed from your code to maintain clarity and efficiency.

        What is the potential impact?

        Having unused local variables in your code can lead to several issues:

        • Decreased Readability: Unused variables can make your code more difficult to read. They add extra lines and complexity, which can distract from the main logic of the code.
        • Misunderstanding: When other developers read your code, they may wonder why a variable is declared but not used. This can lead to confusion and misinterpretation of the code’s intent.
        • Potential for Bugs: If a variable is declared but not used, it might indicate a bug or incomplete code. For example, if you declared a variable intending to use it in a calculation, but then forgot to do so, your program might not work as expected.
        • Maintenance Issues: Unused variables can make code maintenance more difficult. If a programmer sees an unused variable, they might think it is a mistake and try to 'fix' the code, potentially introducing new bugs.
        • Memory Usage: Although modern compilers are smart enough to ignore unused variables, not all compilers do this. In such cases, unused variables take up memory space, leading to inefficient use of resources.

        In summary, unused local variables can make your code less readable, more confusing, and harder to maintain, and they can potentially lead to bugs or inefficient memory use. Therefore, it is best to remove them.

          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Enterprise
          Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use